[Top] [Prev] [Next] [Bottom] [Contents]

Setting Project Options

As indicated earlier, once you have an operating CGI version of your program and a Web Server ready to accept your program as an Application Server and communicate with it, you only need to make some changes in the Project Options of your project and rebuild your project in order to start testing your Application Server.

General

You should verify that the values specified in the Server Extension URLs (ISAPI, NSAPI, and Generic) in the Test and Release tabs of the Project Options Editor are valid. These values should be the same as those you entered into your browser when verifying your server setup earlier. You only need to set up values for those servers you are actually using.

It is highly recommended that you build and test your application using the traditional CGI approach. Only after you have tested your application as a CGI and are happy with the way it works should you convert it to an application server.

After the above steps are taken you can now deploy a Sapphire project as an application server by changing the Makefile.$SA_DEPLOYMENT_TARGET option to something other than CGI. See the picture below for the possibilities. Next you will need to do a Build | Rebuild All on your project and either Install or Test your project.

App Server Options

Cached Connections. Defaulting here to 2, this is the number of connections that can be held open between the Application Server and any particular database between uses of the application server. If an Application Server operates with two different databases, two per database is the limit.
Max Requests. After this many requests the application server will close down automatically.
Timeout. After this period of time (in seconds) with no requests the application server will close down automatically.

Makefile Options

The only change here is to select what type of executable you wish to create:

CGI - Common Gateway Interface
FastCGI - Definition of a faster version of a CGI program
NSAPI - Netscape Application Server; for use with a Netscape Web Server
WRBAPI 2 or 3 - Web Request Broker API. This is for Oracle Cartridges.
Generic Extension - for "other" Web Servers - not Microsoft or Netscape.

If you are creating an Oracle Web Cartridge, remove the exeSuffix definition, leaving it blank. Sapphire/Web will create the executable image with the correct extension.

Test Options

Please refer back to the section on setting up your server while reading this section.

Netscape NSAPI URL Setting

This URL defines the location of the plugin for Netscape NSAPI Application Servers.

http://heartofgold/default.sph

In this case, the above example setting is for a plugin server extension file placed in the document root (HTML root) of a web server called "heartofgold". The file is always called default.sph.

Generic Extension URL

This URL defines the location of the plugin server extension for enabling use of application servers with web servers that do not offer NSAPI compatibility.

http://heartofgold/cgi-bin/SaCGI.cgi

ISAPI URL

Not in use at present

[Top] [Prev] [Next] [Bottom] [Contents]

info@bluestone.com

Copyright © 1997, Bluestone. All rights reserved.